reduced, no new save set will be started until the number of active save
sets running drops below the new value.
When all of the save sets are completed on a client, the client's index
on the NetWorker server will be saved. If the NetWorker server is one of
the machines being saved, its index will be saved after all the other
clients are completely done. When the server's index is saved, the
bootstrap save set information will be printed to the default printer (or
another specified printer). If ssssaaaavvvveeeeggggrrrrpppp detects that the NetWorker server
is not listed in any active group (a group with its autostart attribute
set), then the server's index and bootstrap will be saved with every
group.
The ssssaaaavvvveeeeggggrrrrpppp command will detect other active invocations of the same
group, and will exit with an error message. If two different NetWorker
groups are running simultaneously, they each will run up to _p_a_r_a_l_l_e_l_i_s_m
save sessions simultaneously, however, the NetWorker server will only
allow _p_a_r_a_l_l_e_l_i_s_m of these sessions to write to the backup devices at a
time. Note that running multiple ssssaaaavvvveeeeggggrrrrpppp commands simultaneously can use
up significant server resources, due to the number of pending saves.
The progress of the actively saving clients can be monitored using the
X11 based nnnnwwwwaaaaddddmmmmiiiinnnn(1M) program or the ccccuuuurrrrsssseeeessss(3X) based nnnnssssrrrrwwwwaaaattttcccchhhh(1M)
program. The nnnnssssrrrraaaaddddmmmmiiiinnnn(1M) browser may also be used to examine the
_c_o_m_p_l_e_t_i_o_n status and _w_o_r_k _l_i_s_t of each _N_S_R _g_r_o_u_p resource, although the
_h_i_d_d_e_n attribute display option will need to be selected (see
nnnnssssrrrraaaaddddmmmmiiiinnnn(1M)). These two attributes allows you to track the progress of
each savegrp. See nnnnssssrrrr____ggggrrrroooouuuupppp(4) for more details.
When ssssaaaavvvveeeeggggrrrrpppp starts, it sends an NNNNSSSSRRRR nnnnoooottttiiiiffffiiiiccccaaaattttiiiioooonnnn (see
nnnnssssrrrr____nnnnoooottttiiiiffffiiiiccccaaaattttiiiioooonnnn(4)) with an event of ssssaaaavvvveeeeggggrrrrpppp and priority of iiiinnnnffffoooo to the
NSR notification system. This event is normally logged in the _m_e_s_s_a_g_e_s
attribute of the nnnnssssrrrr____sssseeeerrrrvvvviiiicccceeee(4) resource, and also logged in the log file
specified in the _L_o_g _d_e_f_a_u_l_t NSR notification resource.
When all the save sets have finished, the save sets are automatically
cloned, if the NNNNSSSSRRRR ggggrrrroooouuuupppp resource has the cccclllloooonnnneeeessss attribute enabled.
Clones will be sent to the the pool named in the cccclllloooonnnneeee ppppoooooooollll attribute.
Changing the values of these attributes while ssssaaaavvvveeeeggggrrrrpppp is running has no
effect; they must be set before ssssaaaavvvveeeeggggrrrrpppp starts. The nnnnssssrrrrcccclllloooonnnneeee(1M) command
is used to clone the save sets. Since ssssaaaavvvveeeeggggrrrrpppp uses a heuristic to
determine which save sets were generated as part of the group, it may
occasionally clone more save sets than expected, if a client has its
filesystems separated into multiple groups that run at the same time.
Note that at least two active devices are required to clone save sets.
When the save sets are all complete and cloned (if cloning is enabled),
an NNNNSSSSRRRR nnnnoooottttiiiiffffiiiiccccaaaattttiiiioooonnnn with an event of ssssaaaavvvveeeeggggrrrrpppp and priority of nnnnoooottttiiiicccceeee is
sent to the NSR notification system. This is generally set up to cause
e-mail to be sent to the rrrrooooooootttt user specifying the list of clients who
failed (if any), and all the output collected from all clients. The
format and common error messages included in the savegrp notification are
explained in the SSSSAAAAVVVVEEEEGGGGRRRRPPPP CCCCOOOOMMMMPPPPLLLLEEEETTTTIIIIOOOONNNN NNNNOOOOTTTTIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN MMMMEEEESSSSSSSSAAAAGGGGEEEE section, below.
The aaaassssaaaavvvveeeeggggrrrrpppp command is run only by ssssaaaavvvveeeeggggrrrrpppp, and monitors the progress of
individual save sets. The command line options show which save set and
client is being monitored, and can be viewed using the ppppssss(1) command.
The ----aaaa option shows the authentication type being used, ----TTTT shows the time
before an inactive save set is considered hung, and ----cccc shows the client
being monitored. The ----RRRR option means a filesystem probe is being
performed, and the ----vvvv option requests verbose output from aaaassssaaaavvvveeeeggggrrrrpppp....
Additional information, such as the name of the save set being saved, is
shown after the -------- (double dash) option.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
----EEEE Cause ssssaaaavvvveeee(1M) on each client to estimate the amount of data which
will be generated by each save set before performing it. This will
result in the filesystem trees being walked twice - once to generate
a estimate of how much data would be generated, and again to
generate a save stream to the NetWorker server. Note that the data
is only read from the disk on the final filesystem walk, as the
estimate is performed by using inode information.
----IIII Disable the saving of each client's index.
----OOOO Only save each client's index (for the server, the bootstrap is also
saved).
----mmmm Disable monitor status reporting, including all NNNNSSSSRRRR nnnnoooottttiiiiffffiiiiccccaaaattttiiiioooonnnn
actions.
----nnnn No save. Cause ssssaaaavvvveeee to perform an estimate as described for ----EEEE, but
not to perform any actual saves. This option also sets ----mmmm....
----pppp Run the probe step on each client, so you can see which filesystem
would be saved and at what level, but do not actually save any data.
This option also sets ----mmmm.... The output generated by the ----pppp option may
show several save levels for each save set at different points in
the output, as ssssaaaavvvveeeeggggrrrrpppp learns the correct level. This is the
expected behavior, and can be useful for debugging. The actual
level the savegrp will use will be shown the last time each save set
is shown in the output.
----vvvv Verbose. Print extra information about what ssssaaaavvvveeeeggggrrrrpppp is doing, and
do not pass the ----qqqq flag along to ssssaaaavvvveeee so it too will be chatty.
----GGGG Just run the group; apply no restart semantics. This is the default
mode of operation; the option is provided for compatibility with
other versions of ssssaaaavvvveeeeggggrrrrpppp.
----RRRR Restart. Use the information stored with the NetWorker server to
restart a group which previously was terminated, generally due to a
NNNNSSSSRRRR ggggrrrroooouuuupppp The attribute _w_o_r_k _l_i_s_t contains values in groups of 3,
specifying the client name, level of save, and path to save,
for each save set not yet completed. The attribute
_c_o_m_p_l_e_t_i_o_n contains values in groups of 4, specifying the
client name, path saved, status, and the output, for each
save set completed.
NNNNSSSSRRRR sssscccchhhheeeedddduuuulllleeee Used by the ssssaaaavvvveeeeggggrrrrpppp command with each client's nnnnssssrrrr____cccclllliiiieeeennnntttt(4)
resource to determine which level of save to perform for
each specified save set.
NNNNSSSSRRRR cccclllliiiieeeennnntttt Each client resource names the groups it should be saved by,
the names of the save sets which should be saved, the name
of the schedule to use (see nnnnssssrrrr____sssscccchhhheeeedddduuuulllleeee(4)). and the name
of the directives to use (see nnnnssssrrrr____ddddiiiirrrreeeeccccttttiiiivvvveeee(4)).
